1.1 The Tale of Two Demos ⏱️ 5 min
🎯 Learning Objective
Recognize the difference between demos that fail and demos that close deals.
Every B2B sale with Translab involves a demo. But not all demos are created equal. Let's examine two demos of the same product to the same prospect:
❌ The Demo Disaster
Scenario: Selling Tantor Data Platform to a bank
- Started with product history and architecture
- Showed every single feature (50+ connectors)
- Used generic data samples (not banking)
- No mention of their NPA problem
- CTO asked: "How does this solve our issue?"
- Result: "We'll get back to you" (they didn't)
✅ The Demo Success
Scenario: Same bank, different approach
- Opened with: "Your NPA ratio is 5.2%. Let's reduce it."
- Showed live data: Core Banking + Credit Bureau integration
- Focused on 3 relevant features only
- Walked through their exact use case
- CFO said: "When can we start?"
- Result: POC approved on the spot
🔍 Interactive: What Went Wrong?
Click each card to reveal the specific mistake and why it kills deals:
1.2 The McKinsey Pyramid Principle ⏱️ 5 min
🎯 Learning Objective
Apply the Pyramid Principle to structure demos that lead with impact.
Barbara Minto's Pyramid Principle: Start with the answer, then support with evidence. Executives don't have time to "discover" your point—tell them first.
🏗️ Build Your Demo Pyramid
Click the options below to place them in the correct pyramid level:
Why Pyramid Works in B2B Sales
- 6-7 decision-makers in typical buying committees means people join late, leave early, and get distracted. Lead with impact so your key message lands even if someone misses half the demo.
- Executives test you — if you can't articulate value in 30 seconds, you fail their mental filter
- Interruptions are common — pyramid ensures your key message is delivered first, before the meeting gets derailed
2.1 Discovery-to-Demo Mapping ⏱️ 5 min
🎯 Learning Objective
Translate discovery insights directly into demo focus areas.
Great demos aren't planned in isolation—they're mapped directly from discovery. Every pain point the prospect shared = a demo moment.
The Translation Framework
| What You Heard | Translation | Demo Focus |
|---|---|---|
| "Regulatory reports take 2 weeks" | Manual data aggregation pain | Tantor: Automated CIMS reporting |
| "We have 12 different data silos" | Data fragmentation problem | Tantor: Data fabric + CDC |
| "API response times inconsistent" | API management issue | Kong: Analytics + rate limiting |
| "Need to provision across AWS, Azure, GCP" | Multi-cloud complexity | HashiCorp: Terraform multi-cloud |
| "GenAI apps need real-time vector search" | Database performance for AI | DataStax: Astra vector search |
🎮 Interactive: Map the Pain Points
Drag each pain point to the correct Translab solution:
📊 Tantor Data Platform
🤖 Tantor AI Platform
🔌 Kong API Gateway
🏗️ HashiCorp Terraform
💾 DataStax Astra DB
2.2 The Rule of 3s & MECE ⏱️ 5 min
🎯 Learning Objective
Apply BCG's "Rule of 3s" and McKinsey's MECE framework to demo structure.
BCG's Rule of 3s
Cognitive load research shows people remember 3-4 items best. Show 3 key capabilities, not 30. More features = less retention.
McKinsey's MECE Principle
Mutually Exclusive, Collectively Exhaustive: Organize your demo into non-overlapping sections that cover everything the prospect needs to see.
Demo Structure Template (MECE)
- Problem Statement (2 min) - Restate their pain in their words
- Solution Overview (3 min) - High-level "how we solve it"
- Live Demonstration (10-15 min) - Show 3 key capabilities
- Business Impact (3 min) - ROI, metrics, outcomes
- Next Steps (2 min) - POC scope, timeline
🔎 Spot the Violation
Which of these demo approaches violates the Rule of 3s? Click the violator:
Demo A: Kong Gateway
"Today I'll show you three things: Rate limiting, authentication, and performance analytics."
Demo B: Tantor Data
"Let me walk you through all 50 connectors, our CDC engine, data lineage, governance, catalog, quality rules, masking, profiling, and orchestration..."
Demo C: DataStax
"For your GenAI use case, I'll focus on: Vector search performance, multi-region replication, and Langflow integration."
3.1 The Technical Buyer ⏱️ 5 min
🎯 Learning Objective
Customize demos for CTOs, CIOs, VPs of Engineering, and technical evaluators.
🔧 Technical Buyer Profile
Who: CTO, CIO, VP Engineering, IT Director, Lead Architect
What They Care About: Architecture, scalability, security, integration, maintenance
Demo Duration: 20-25 minutes (they'll ask detailed questions)
Technical Buyer Demo Structure
| Time | Section | What to Show |
|---|---|---|
| 5 min | Architecture Overview | System diagram, deployment options, tech stack |
| 10 min | Live Technical Demo | APIs, configurations, integrations with their systems |
| 5 min | Security & Compliance | Encryption, RBAC, audit logs, certifications |
| 5 min | Operations & Support | Monitoring, maintenance, SLAs, documentation |
🎬 Scenario: What Do You Show First?
You're demoing Tantor Data Platform to a CTO who asked: "How does this integrate with our Oracle Core Banking system?"
Click your choice:
- Don't oversimplify—they'll think you don't understand their complexity
- Don't hide limitations—they'll find them. Be honest, show workarounds.
- Don't skip the "how"—they need to explain it to their team
3.2 Economic & End-User Buyers ⏱️ 5 min
🎯 Learning Objective
Customize demos for CFOs (economic) and Data Engineers/Analysts (end-users).
💰 Economic Buyer Profile
Who: CFO, CEO, COO, VP Finance
What They Care About: ROI, TCO, risk, time-to-value
Demo Duration: 10-15 minutes (shorter, higher-level)
Key Question: "What's the business impact?"
👤 End-User Buyer Profile
Who: Data Engineers, Analysts, Operations
What They Care About: Day-to-day usability, learning curve
Demo Duration: 15-20 minutes (hands-on)
Key Question: "How will this make my job easier?"
🎮 Match the Demo Approach
Drag each demo element to the right buyer persona:
🔧 Technical
💰 Economic
👤 End-User
Multi-Stakeholder Strategy
With 6-7 decision-makers in typical buying committees, you'll often present to mixed audiences. Use this layered approach:
- Open with CFO framing (2 min) - Business impact headline
- Show end-user workflow (5 min) - Day-in-the-life keeps everyone engaged
- Address CTO architecture (5 min) - Technical validation
- Close with ROI (3 min) - Economic justification
4.1 The Pre-Demo Checklist ⏱️ 5 min
🎯 Learning Objective
Build a systematic pre-demo preparation routine that eliminates failures.
✅ Build Your Pre-Demo Checklist
Practice checking off each item as you would before a real demo:
📋 Research & Intel
🎯 Demo Customization
🔧 Technical Prep
📤 Materials & Next Steps
4.2 Product-Specific Demo Prep ⏱️ 5 min
🎯 Learning Objective
Know the specific preparation steps for each Translab product.
Click each card to reveal product-specific demo prep tips:
📊 Tantor Data Platform
CDC, Data Fabric, 50+ Connectors
Tantor Data Prep
- Pre-configure connectors for their sources (Oracle, SQL Server)
- Load banking/healthcare sample data
- Test CDC lag times
- Prepare data lineage visualization
🤖 Tantor AI Platform
20+ AI Agents, AutoML, Governance
Tantor AI Prep
- Select 2-3 agents for their use case
- Prepare ROI calculator with their numbers
- Show governance dashboard
- Have competitor comparison ready
🔌 Kong API Gateway
API Management, Service Mesh
Kong Prep
- Map their API traffic patterns
- Demo rate limiting with realistic thresholds
- Show relevant plugins (auth, logging)
- Prepare Kong + Tantor integration story
💾 DataStax Astra DB
NoSQL, Vector DB for GenAI
DataStax Prep
- Show vector search for GenAI use cases
- Demo multi-region replication
- Highlight Langflow for AI prototyping
- Prepare MongoDB/Cassandra comparison
🏗️ HashiCorp Terraform
Infrastructure-as-Code, Vault
HashiCorp Prep
- Create multi-cloud example (AWS+Azure)
- Show state management, drift detection
- Demo Vault for secrets management
- Discuss migration services
☁️ Cloudera
Enterprise Data Platform
Cloudera Prep
- Show self-service data provisioning
- Demo workload optimization (Spark, Hive)
- Highlight hybrid cloud portability
- Address Hadoop migration concerns
🎓 Knowledge Check Quiz ⏱️ 5 min
Test Your Learning
Passing Score: 4 out of 6 questions (67%)
Scenario-based questions reflecting real B2B demo situations.
🎯 Key Takeaways ⏱️ 3 min
Module 5, Section 1: Demo Planning & Customization
Core Principles:
- Pyramid Principle: Start with the answer (business impact), then support with evidence. Never bury the lead.
- Discovery Drives Demos: Every pain point from discovery = a demo moment. Generic demos fail.
- Rule of 3s: Show 3 key capabilities, not 30. Cognitive overload kills retention.
- MECE Structure: Mutually exclusive, collectively exhaustive sections with no overlaps.
Persona-Based Customization:
- Technical Buyers (CTO/CIO): Architecture, APIs, security, integrations
- Economic Buyers (CFO/CEO): ROI, TCO, risk mitigation, time-to-value
- End-Users (Engineers/Analysts): Day-in-the-life workflows, ease of use
Pre-Demo Essentials:
- ✅ Research attendees & review discovery notes
- ✅ Customize scenario with industry-specific data
- ✅ Test environment & prepare fallback
- ✅ Define success criteria & next steps
Multi-Stakeholder Strategy:
- Open with CFO framing (business impact)
- Show end-user workflow (keeps everyone engaged)
- Address CTO architecture (technical validation)
- Close with ROI (economic justification)
🎉 Section 1 Complete!
You've mastered demo planning and customization. Next up: Section 2 - Presentation Design & Storytelling.